One of the most misunderstood concepts in project scheduling is the difference between schedule variance and construction delay analysis.
Many planners and project managers assume that if an activity shows a variance in Primavera P6 or Microsoft Project, that variance represents the delay caused to the project.
Organizations seeking Offshore Project Controls Services often discover that schedule variance alone cannot determine project delay responsibility or support construction claims.Unfortunately, that assumption is incorrect.
Variance Measures Date Difference. Forensic Delay Analysis Measures Project Impact.
Understanding this difference is critical for construction claims, extension of time requests, arbitration, and project recovery planning.
What is Schedule Variance?
In Primavera P6 and Microsoft Project:
Schedule Variance = Actual Date – Baseline Date
Example 1
- Planned Start: 01-Jan
- Actual Start: 10-Jan
- Variance = 9 Days
Example 2
- Planned Finish: 30-Jan
- Actual Finish: 10-Feb
- Variance = 11 Days
While these variances indicate slippage, they do not tell us:
- Whether the delay affected the critical path
- Whether the delay impacted project completion
- How many days of project delay were caused
- Who is responsible for the delay
This is where Forensic Delay Analysis becomes important.
This is where construction delay analysis becomes essential for identifying delay responsibility and quantifying project impact.
What is Forensic Delay Analysis?
Forensic Delay Analysis is a structured methodology used to determine:
- The existence of delay
- The cause of delay
- The responsibility for delay
- The impact of delay on project completion
It is extensively used in:
- Construction Claims
- Extension of Time (EOT) Requests
- Arbitration
- Litigation
- Schedule Recovery Planning
The objective is simple:
Determine How Many Days a Particular Event Delayed the Project.
How Does Forensic Delay Analysis Work?
One common technique involves introducing a delay fragment (fragnet) into the approved Primavera P6 schedule.
A fragnet is a miniature network of activities representing the delaying event.
Step 1 – Insert Delay Fragnet
Examples include:
- Design Approval Delay
- Material Delivery Delay
- Weather Disruption
- Change Order Delay
- Procurement Delay
Step 2 – Connect the Fragnet
- Activities affected by the delay
- Predecessors causing the delay
- Successors impacted by the delay
Step 3 – Reschedule the Program
The schedule is recalculated.
Step 4 – Measure Project Finish Impact
The difference between:
- Original Completion Date
- New Completion Date
represents the actual delay impact.
This delay may be:
- 0 Days
- 5 Days
- 30 Days
- 100 Days
depending on schedule logic and critical path movement.
This is the actual project delay—not the variance.
Why Variance Does Not Measure Delay
Consider an activity delayed by 30 days.
Many planners immediately conclude:
"The Project Is Delayed By 30 Days."
Not necessarily.
If the activity:
- Is Non-Critical
- Has Available Float
- Does Not Drive Project Completion
The project delay may actually be:
0 Days
Conversely, a 5-day delay on a critical path activity may cause:
5 Days Project Delay
Therefore:
Activity Variance ≠ Project Delay
Major Types of Delay Analysis
1. Impacted As-Planned Analysis
- Insert delay fragnet into baseline schedule
- Measure completion impact
- Simple and widely used
2. Time Impact Analysis (TIA)
Industry-preferred methodology.
- Insert delay event into schedule update
- Measure impact prospectively
- Used for change orders and EOT claims
3. Collapsed As-Built Analysis
- Start with actual completed schedule
- Remove delaying events
- Determine hypothetical completion date
4. As-Planned vs As-Built Analysis
Compares baseline schedule against actual completion.
5. Windows Analysis
One of the most reliable delay analysis methodologies.
- Divide project into periods
- Analyze critical path movement
- Track evolving project conditions
6. Contemporaneous Period Analysis
Analyzes schedule updates period-by-period.
7. Earned Schedule Analysis
Uses earned value and schedule metrics to forecast future delays.
Which Delay Analysis Method Is Best?
There is no universal answer.
The appropriate methodology depends on:
- Contract Requirements
- Schedule Quality
- Available Updates
- Claim Type
- Legal Jurisdiction
However, the most widely accepted methods are:
- ✔ Time Impact Analysis (TIA)
- ✔ Windows Analysis
- ✔ Contemporaneous Period Analysis
Why US Contractors Need Professional Delay Analysis
Construction disputes are becoming increasingly schedule-driven.
Owners, contractors, attorneys, and project managers require:
- Defensible Delay Calculations
- Extension of Time Support
- Construction Claims Preparation
- Schedule Recovery Planning
- Independent Project Controls Reviews
A poorly prepared delay claim can result in:
- Rejected EOT Requests
- Unrecoverable Costs
- Contract Disputes
- Arbitration Challenges
Professional forensic analysis helps establish facts rather than assumptions.
How EBEESCORP Supports US Construction Teams
We provide offshore Project Controls and Delay Analysis Services for:
- Primavera P6 Scheduling Services USA
- Baseline Development
- Schedule Updates
- Critical Path Reviews
- Forensic Delay Analysis
- Time Impact Analysis (TIA)
- Construction Claims Support
- Extension of Time Analysis
- Schedule Recovery Planning
- Executive Dashboard Reporting
Need Independent Schedule Review or Delay Analysis?
EBEESCORP supports US Contractors, EPC Companies, Construction Managers and Project Owners with Project Controls, Construction Claims Support and Primavera P6 Scheduling Services.